Skip to content

feat: suggestion of more optimum settings for postgres #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
gilescope wants to merge 2 commits into
base: main
Choose a base branch
from
Open

feat: suggestion of more optimum settings for postgres #23

gilescope wants to merge 2 commits into from

Conversation

@gilescope
Copy link
Collaborator

@gilescope gilescope commented May 26, 2025 •
edited
Loading

Fixes #16

Potentially this could improve people's db-sync speeds. If people want to comment back on their experiences using this PR that would be helpful.

@gilescope gilescope requested a review from a team as a code owner May 26, 2025 15:20
@github-actions
Copy link

github-actions bot commented May 26, 2025 •
edited
Loading

Logo
Checkmarx One – Scan Summary & Details – 561257f4-ced7-4748-88d0-d5253f8f8fad

New Issues (8)

Checkmarx found the following issues in this Pull Request

Severity Issue Source File / Package Checkmarx Insight
MEDIUM Container Capabilities Unrestricted /compose-partner-chains.yml: 76
detailsSome capabilities are not needed in certain (or any) containers. Make sure that you only add capabilities that your container needs. Drop unnec...
ID: NJUPwWnM3VTyqB%2FJBN9ndeWlJ%2FE%3D
MEDIUM Container Capabilities Unrestricted /compose-partner-chains.yml: 57
detailsSome capabilities are not needed in certain (or any) containers. Make sure that you only add capabilities that your container needs. Drop unnec...
ID: OVSHTdZ6%2B%2BzQzqzLq7XFot8yrVQ%3D
MEDIUM Container Traffic Not Bound To Host Interface /compose-partner-chains.yml: 49
detailsIncoming container traffic should be bound to a specific host interface
ID: XuVH8tmh%2FhtVyNa7B9gyG1Xeo3k%3D
MEDIUM Container Traffic Not Bound To Host Interface /compose-partner-chains.yml: 83
detailsIncoming container traffic should be bound to a specific host interface
ID: nLVbQNsDPz2pKWI6YFTiTlGKaSc%3D
MEDIUM Healthcheck Not Set /compose-partner-chains.yml: 76
detailsCheck containers periodically to see if they are running properly.
ID: eRBSHqBJVZRruPQ0F0fCO0D7Q%2FI%3D
MEDIUM Healthcheck Not Set /compose-partner-chains.yml: 57
detailsCheck containers periodically to see if they are running properly.
ID: tQg1k5Yi19tvWQpjJu%2F%2B3aE7rHs%3D
MEDIUM Security Opt Not Set /compose-partner-chains.yml: 57
detailsAttribute 'security_opt' should be defined.
ID: %2FQe94qkO8vDncOKYV56njJUi7AA%3D
MEDIUM Security Opt Not Set /compose-partner-chains.yml: 76
detailsAttribute 'security_opt' should be defined.
ID: TLYSfFv4G0dp0bDCjeMpPQpN%2FlI%3D
Fixed Issues (8)

Great job! The following issues were fixed in this Pull Request

Severity Issue Source File / Package
MEDIUM Container Capabilities Unrestricted /compose-partner-chains.yml: 55
MEDIUM Container Capabilities Unrestricted /compose-partner-chains.yml: 74
MEDIUM Container Traffic Not Bound To Host Interface /compose-partner-chains.yml: 81
MEDIUM Container Traffic Not Bound To Host Interface /compose-partner-chains.yml: 47
MEDIUM Healthcheck Not Set /compose-partner-chains.yml: 74
MEDIUM Healthcheck Not Set /compose-partner-chains.yml: 55
MEDIUM Security Opt Not Set /compose-partner-chains.yml: 55
MEDIUM Security Opt Not Set /compose-partner-chains.yml: 74

@gilescope gilescope mentioned this pull request May 27, 2025
Open
@gilescope
Merge branch 'main' into giles-postgres-config
9eaa590 
Signed-off-by: Squirrel <gilescope@gmail.com>
@CLAassistant
Copy link

CLAassistant commented Nov 26, 2025 •
edited
Loading

CLA assistant check
All committers have signed the CLA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Optimise postgres

3 participants

@gilescope @CLAassistant